Issue being fixed or feature implemented

The previous proof system was causing issues for proofs with limits in Platform, these issues would cause proofs to cause failures in the system. As it was built by someone no longer with the project we needed to either understand how it worked or rewrite it. Understanding how it worked proved to be phenomenally hard to achieve, so instead a new GroveDB
proof system was devised.

What was done?

Introduced Proof System V1. This proof system resolves around recursive GroveDB proof layers. Each proof layer represents a merk and can have sublayers if we want to query subtrees.

Proofs are no longer verbose/non verbose, instead you just simply need to set in your proof verification options that you are querying a subsection of the proof.

Proofs also can no longer have offsets. Offsets never really worked with proofs as they can balloon proofs. It was an architectural mistake to every have offsets and this is now fixed. Instead users should use proper ranges that were offset by the end value of previous requests.

How Has This Been Tested?

Many many tests were written, also it passes all platform tests, and also solves the issues we were experiencing in platform.

Breaking Changes

Since this is a new proof system, it represents a breaking change to Platform.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone